-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Add packagePoliceDelete
callback
#148509
[Fleet] Add packagePoliceDelete
callback
#148509
Conversation
Pinging @elastic/fleet (Team:Fleet) |
packagePolicyPostDelete
and packagePoliceDelete
callbackpackagePoliceDelete
callback (rename existing packagePoliceDelete
to packagePolicyPostDelete
)
packagePoliceDelete
callback (rename existing packagePoliceDelete
to packagePolicyPostDelete
)packagePoliceDelete
callback
@dhurley14 Can you help me understand why the security tests fail, and how to fix them?
My changes are mostly type related. Only runtime impacting change is renaming 'postPackagePolicyDelete' to 'packagePolicyPostDelete'. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - cloud security posture.
@orouz Would you like to double verify me?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OLM changes look good to me 👍
@sqren it seems like those cypress tests are failing on other PR's as well.. We will look into it. |
d7afb4e
to
0d18523
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fleet changes looks good to me 🚀
922a2de
to
8e763f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@sqren I think someone from @elastic/security-threat-hunting should be able to help investigate the flakiness of the other cypress tests. I'm looking into why the exceptions one is failing on your branch. |
That would be great, thanks. I'll try to re-run the build but will post the failing tests here for visibility
|
Buildkite, test this |
Add tests Rename `PackagePolicyPostCreateCallback` back to `PostPackagePolicyPostCreateCallback` Rename `PackagePolicyCreateCallback` back to `PostPackagePolicyCreateCallback` Add “Post” prefix Use `packagePolicyService.getByIDs`
8e763f9
to
958b253
Compare
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
Public APIs missing exports
History
To update your PR or re-run it, just comment with: |
Closes elastic#146368 Depends on: elastic#148509 This adds an api key to every APM package policy. This will make it possible for APM Server to query the source map index ( `.apm-source-map` ) and the agent config index (`.apm-agent-configuration`)
Required by: #147650
This PR adds a callback that runs just before a package policy is deleted. This is needed for the APM package (and possible other use cases) where API keys embedded in the package policy will need to be deleted/invalidated so they don't linger in the system after the policy has been removed.
The new callback is called
packagePoliceDelete
. A delete callback already exists, however, this callback is called after the policy is deleted.Renaming in this PR:
postPackagePolicyDelete
->packagePolicyPostDelete
DeletePackagePoliciesResponse
->PostDeletePackagePoliciesResponse
PostPackagePolicyDeleteCallback
->PostPackagePolicyPostDeleteCallback